Click Here!
home account info subscribe login search My ITKnowledge FAQ/help site map contact us


 
Brief Full
 Advanced
      Search
 Search Tips
To access the contents, click the chapter and section titles.

Sams Teach Yourself MCSE Windows NT Server 4 in 14 Days
(Publisher: Macmillan Computer Publishing)
Author(s): David Schaer, et al
ISBN: 0672311283
Publication Date: 12/15/97

Bookmark It

Search this book:
 
Previous Table of Contents Next


The following conditions must be met before the administrator can use the NetWare Migration Tool:

1.  The target NT server must be a domain controller if you are migrating users.
2.  If you will be using NWCONV to migrate files to NT and want to retain permissions, the destination partition on the NT server must be formatted using NTFS.
3.  NWLink must be appropriately configured and the Gateway Service for NetWare (GSNW) must be installed on the NT server as an active service.
4.  The NT administrator must know the name and password to the NetWare supervisor account (or supervisor equivalent account) to perform the migration.

Preparing the NetWare Server

When preparing the NetWare server for migration, remember the old adage “Garbage in, garbage out.” Make certain the source data reflects the way you want it in the NT environment. Although not entirely necessary, exercising a little cautious optimism goes a long way in ensuring data integrity.

1.  Perform routine file system maintenance. Weed unnecessary files on any volume that is to be migrated. Purge the volume and back it up.
2.  Perform user/group object maintenance. Crank up NWADMIN or SYSCON and remove inactive user accounts and groups. Be wary of duplicate user or group objects on 3.1x servers if you plan to migrate multiple 3.1x servers; such duplication will cause errors in the NT migration process. Perform any group assignments or security modifications you’ve been putting off before running a live migration.
3.  Repair the NDS/bindery. In a NetWare 4.1x environment, run DSREPAIR to fix any invisible problems in the NDS and synchronize all servers in all replicas (if applicable). On your NetWare 3.1x server, run BINDFIX to verify the integrity of the NetWare bindery.
4.  Perform an NLM audit. NetWare Loadable Modules are server-side programs launched from the NetWare system console and are not migrated to Windows NT, but they may be critical to some level of user functionality. Review the NLMs loaded on your server and secure the NT equivalents if necessary.
5.  Perform a client-side audit of file and print services. Remember that UNC locations on your clients change after the migration. NPRINTERS and PSERVERS are inactive after the Novell box is shut down, and device mappings not handled through logon scripts may be adversely affected after the migration. Perform the audit before your migration to guarantee that user functions aren’t disabled after moving to Windows NT.

12.5. Starting the NetWare Migration Tool

From the Windows NT desktop, access the NWCONV.EXE shortcut from the Administrative Tools folder found under the program group as shown in Figure 12.13.


Figure 12.13.  Selecting the Migration Tool for NetWare.

When the migration tool is launched, you see the Select Servers For Migration dialog box, where you identify the source NetWare server and target NT server involved in the migration (see Figure 12.14).


Figure 12.14.  Designate the NetWare Server (source) and Windows NT Server (target).

Either manually enter the UNC to the desired NetWare server or select the ellipses button t o browse to the server as shown in Figure 12.15.

Using the interface, highlight the desired NetWare server and click the OK button. You return to the Select Servers For Migration dialog box.

Next, identify the target NT server. After selecting the target NT server, you return to the Select Servers For Migration dialog box. Both the NetWare server and NT server should be identified. Click OK to continue.

At this time, NWCONV verifies your current access restrictions to the NetWare server. If your current account is not a supervisor equivalent on the specified NetWare server, you see the Enter Network Credentials dialog box (see Figure 12.16). You must provide a NetWare supervisor account and password or you return to the Select Servers For Migration dialog box. Click OK to continue.


Figure 12.15.  Select your server from the browse list.


Figure 12.16.  Enter NetWare credentials for access to the NetWare server.

After the credentials verification, you see the main Migration Tool for NetWare dialog box (see Figure 12.17). The servers you specified are listed in the left columns as the first set involved in the migration process. If you want, you can add more servers using the selection process just described or you can delete additional servers before continuing.


Figure 12.17.  Both the source (NetWare) and target (Windows NT) servers have been selected.

Adding additional servers is practical only in a NetWare 3.1x environment where multiple servers contain different bindery objects. In a NetWare 4.1x environment, you need only specify an NDS server to capture all the user objects in your environment.

On the Migration Tool for Netware dialog box, you see two option buttons for customizing the migration process for files and users. When you select the User Options button, the User and Group Options dialog box displays.

12.6. Selecting User and Group Migration Options

The User and Group options enable you to control how user and group objects are imported into the domain controller. You can specify how the migration tool handles password assignments, duplications in user or group names, whether NetWare account restrictions should be migrated, and whether NetWare supervisors should be added to the Administrator group on the NT server. You choose options by clicking radio buttons, completing entry fields, or toggling checkmarks under four tabs in the User and Group Options dialog box.

12.6.1. User and Group Migration Options: Passwords

You cannot migrate NetWare passwords to Windows NT using NWCONV. The Passwords tab of the User and Group Options dialog box presents three options (see Figure 12.18):

  No Password: No password assignment.
  Password is Username: The account username is appended as a password.
  Password is [password]: The administrator can specify one password to be as signed to all migrated user accounts.

The checkbox at the bottom of the dialog box enables you to flag password assignments as temporary on the NT server, forcing the user to change the password at the next logon.


Figure 12.18.  Selecting User and Group options for passwords.


Previous Table of Contents Next


Products |  Contact Us |  About Us |  Privacy  |  Ad Info  |  Home

Use of this site is subject to certain Terms & Conditions, Copyright © 1996-2000 EarthWeb Inc.
All rights reserved. Reproduction whole or in part in any form or medium without express written permission of EarthWeb is prohibited.